Determining, Displaying and Using Tape Drive Session Information

ABSTRACT

Methods and systems for monitoring libraries and library drives. In one embodiment, a method is provided which includes polling the library to determine whether a storage media has been loaded in to, or unloaded from, a drive. When the media has been loaded, the method includes beginning a media monitoring session. The method may include determining which tape has been loaded in to which drive of the library and associating the session performance with that tape and that drive. Some embodiments include using a Read Element Status command to perform the polling. In some examples, the library is a magnetic tape library and the polling is performed out-of-band. Information regarding the media sessions can be output in order of session performance. Some embodiments include determining whether the cause of a slow session is external to the library and correcting the external cause.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims a benefit of priorityunder 35 U.S.C. 120 of the filing date of U.S. patent application Ser.No. 12/025,300, filed on Feb. 4, 2008, “Determining, Displaying, andUsing Tape Drive Session Information”, the entire contents of which arehereby expressly incorporated by reference for all purposes.

TECHNICAL FIELD OF THE INVENTION

The present disclosure relates to methods and systems for monitoringstorage components. More particularly, an embodiment relates to methodsand systems for monitoring library performance by identifying librarytape sessions in a non-intrusive manner using an out-of-band appliance.

BACKGROUND

Data represents a significant asset for many entities. Consequently,data loss, whether accidental or caused by malicious activity, can becostly in terms of wasted manpower, loss of goodwill from customers,loss of time and potential legal liability. To ensure proper protectionof data for business and legal purposes, many entities back up data to aphysical storage media such as magnetic tapes or optical disks.Traditionally, backup would occur at each machine controlled by anentity. As the sophistication of network technology increased, manyentities turned to enterprise level backup in which data from multiplemachines on a network is backed up to a remote library. Typically, alibrary includes a variety of components which include a plurality ofmedia for data storage, e.g., multiple magnetic tapes. Centralized databackup has the advantage of increased volume, efficiency, andredundancy.

In many systems, the data to be backed up and backup commands are sentover a network from multiple machines on the network to a library. Inmany instances, the data to be backed up and the backup commands arerouted to the library through a switch.

One example of a library commonly used in enterprise backup systems is amagnetic tape library. A magnetic tape library can comprise componentssuch as tape cartridges (containing magnetic tape), robots, tape slotsand tape drives. A typical magnetic tape library contains multiplecartridge slots in which tape cartridges can be stored. Tape cartridges,commonly referred to as tapes, are physically moved between cartridgeslots and tape drives by a robot. The robot is controlled by commandsreceived from the host devices on the network. When specific data isrequired, a host device determines which cartridge slot contains thetape cartridge that holds the desired data. The host device thentransmits a move-element command to the robot and the robot moves thetape cartridge to a tape drive which reads the desired data from thetape cartridge.

In a SCSI tape library, devices that are part of the library aretypically addressed by target number. Thus, each drive and robot of atape library typically has a target number. Cartridge slots, on theother hand, are addressed by element numbers that are used by the robotto locate the slots. Because the robot also places tape cartridges inthe drives, each drive is also associated with an element number.

Components of a library are subject to wear and other forms ofdegradation which may degrade individual library component(s) to a pointwhere the degraded component(s) can no longer be reliably used.Degradation of library components may render a library unreliable andprone to data loss, diminishing the library's usefulness as a backupdevice. The failing of even one library component can cause the loss ofvaluable data. Furthermore, the process of determining which librarycomponent is failing and rendering the library unreliable can be timeconsuming, uncertain and expensive. Networks and other equipmentexternal to the library may also affect the performance of the library.For instance, if data is being backed up from a remote location,transport delays and interruptions along the transmission path may causethe data to arrive relatively slowly (or not at all) at the library.While the library may store the data just as fast as it arrives, theperformance of the library suffers because the storage rate in thesecircumstances is nonetheless slow.

SUMMARY

Embodiments disclosed provide methods and systems of monitoring libraryperformance that eliminate, or at least substantially reduce, theshortcomings of prior art library systems and methods. Some embodimentsinclude polling a library to determine whether a media (e.g., tape,optical disk, or other media) has been loaded or unloaded between polls.When it is discovered that a media has been loaded a media session isbegun. Performance data (e.g., data transfer speed, error rates, etc)associated with the media session is monitored. When it is determinedthat the tape has been unloaded, the media session ends. Informationregarding the media session for instance, performance relatedinformation, can be output and stored for subsequent use.

Back up system topologies vary widely. For instance, in someembodiments, data may flow to the back up system, its library(s), anddrive(s) from multiple points of a network. In many back up systems,each tape may be placed in any drive capable of reading that tape andany drive may be used to read any compatible tape in the library. Duringa back up job, and over the course of time, an individual tape may beloaded in to many different drives and an individual drive may have manydifferent tapes loaded in to it. These factors may contribute to, mask,or have little effect on the cause(s) of differing library performancebetween tape sessions. For instance, jobs (e.g., a data write to thetape or a data read from the tape) associated with a particular tapemight suffer comparatively low library performance in which case thetape becomes suspect. In other circumstances, jobs associated with aparticular drive might suffer comparatively low library performance inwhich case the drive becomes suspect. In other cases, the lowperformance jobs may exhibit no apparent pattern with regard to eitherthe tapes or the drives in which case it may be useful to associate thelow performance with the tape session rather than the tape or the driveinvolved. Users and owners of storage area networks, back up systems,libraries, drives, tapes, and the data thereon are interested in knowingthe performance of these systems as a whole as well as the individualcomponents of these systems. This knowledge can aid in troubleshootingfailures, troubleshooting slow performing sessions, and in optimizingsystem performance and utilization.

The methods of some embodiments monitor the performance of back upsystems, libraries, and operations and associate information withidentified tape sessions. A tape session can begin when a tape is loadedin to a drive and can continue until the tape is unloaded. Informationcan be collected regarding the tape session to allow a user to optimizethe performance and utilization of the systems and components involved.The methods of some embodiments gather information such as the amount ofdata transferred per time period, the types and numbers of errorsoccurring during a time period, and the identities of the tapes anddrives used during a time period. The gathered information can allowinterested parties to understand and improve the performance andutilization of the back up system.

In some embodiments that use a robot (or other automated tape handlingmechanism) to load and unload tapes in a library, the library can beperiodically polled to determine the position of the tapes in thelibrary. Information from consecutive polls can be examined and used togenerate a list of tape movements in the library. For instance, if atape in a first poll was not in a tape drive and the tape upon a secondpoll is in a tape drive, the beginning of a tape session may bedeclared. If a tape was in a tape drive in a first poll and the tape isnot in the tape drive upon a second poll, the end of a tape session canbe declared. In some embodiments, the system can use the SCSI ReadElement Status command to implement the polls.

In some embodiments without automatic tape handling mechanisms (e.g.,embodiments which include a freestanding tape drive) the tape drive canbe periodically polled to determine if a tape has been loaded in to anyof the drives. By examining differences between consecutive polls, alist of tape movements in to and out of the tape drives can begenerated. If a tape drive in a first poll reported that no tape was inthe drive and the drive reports that a tape is in the tape drive upon asecond poll, the beginning of a tape session can be declared. If a tapedrive in a first poll reported that a tape was in the drive and thedrive reports that no tape is in the tape drive upon a second poll, theend of the tape session can be declared. In some embodiments, the SCSIRead Media Serial Number command can be used to implement the polls.

During the tape sessions, in some embodiments, information can begathered regarding the session. Examples of such information include,but are not limited to, the amount of data written and read, the numberof errors encountered, and the start and end times of the session. Thegathered information can be stored in a database and additionalinformation can be gathered or calculated. Examples of calculatedinformation include (but are not limited to) the duration and theaverage data transfer rate of the tape sessions. Additional measurementsof system performance can also be gathered or derived.

The tape drive and the tape used for a given tape session can beidentified in some embodiments. Information can be gathered during thetape sessions and can be associated with the tape drive, the tape, thetape session, or any combination thereof. In some embodiments, a list oftape sessions grouped by tape drives, a collection of tape drives,tapes, time periods, or other considerations can be displayed. Forexample, errors can be grouped by tape session and can be used topinpoint the source of problems associated with the tape drives andtapes in use for the tape sessions. Some embodiments provideinformational listings of tape sessions. Users can examine the listingsto determine whether particular tape sessions were the source of mostperformance issues or whether the performance issues correspond to someother phenomenon. Information can be gathered that may be useful indistinguishing between low performance tapes, tape drives, and tapesessions.

Some embodiments provide outputs such as user selected tables of tapesession information. Notifications based on user selected tape sessioncharacteristics can also be provided. Systems of some embodiments cansort the sessions by performance and list the worst performing sessionsfor the user. Users can analyze this tape session information toidentify low performing sessions. For example, the user (e.g., thelibrary administrator) can determine the source of the data that wasbeing backed up during the low performing session. The user can improvethe data connection speed between the data source and the tape drive.The next time the same data source writes to a tape, the user canexamine the speed of the new tape session to verify whether systemperformance improved. By eliminating the low performing sessions, theuser can forestall purchase of new library equipment by getting moreperformance out of existing equipment.

Embodiments of the disclosure provide many advantages. For instance,some embodiments allow the user to determine the performance of a set oftapes and tape drives. For another example, some embodiments allow theuser to identify low performing tape sessions and eliminate the causesthereof from the back up environment. The identification of lowperforming sessions also allows users to identify inefficiencies inbackup jobs. Users may also improve the performance of components in thebackup system. Other advantages include allowing users to identify datasources that can be backed up by a drive closer to the data source.Still further advantages include allowing users to improve the time ittakes to complete a set of back ups and to avoid damaging drives byrunning the drives below their recommended streaming rates. Overall backup performance can also be improved by identifying the worst sessionsand eliminating the causes thereof.

BRIEF DESCRIPTION OF THE FIGURES

A more complete understanding of the disclosure and the advantagesthereof may be acquired by referring to the following description, takenin conjunction with the accompanying drawings in which like referencenumbers generally indicate like features and wherein:

FIG. 1 is a diagrammatic representation of one embodiment of a library.

FIG. 2 is a diagrammatic representation of one embodiment of a backupsystem using a library and having a monitoring appliance.

FIG. 3 is a diagrammatic representation of one embodiment of acontroller which can be used in a monitoring appliance.

FIG. 4 is a flowchart illustrating an embodiment of a method formonitoring libraries.

FIG. 5 is a diagrammatic representation of a tape session.

FIG. 6 illustrates a report of a monitoring appliance.

FIG. 7 illustrates another report of a monitoring appliance.

FIG. 8 is a flowchart illustrating another embodiment of a method of formonitoring libraries.

DETAILED DESCRIPTION

Preferred embodiments of the disclosure are illustrated in the FIGURES,like numerals being used to refer to like and corresponding parts of thevarious drawings.

Various embodiments provide a method and system for classifyinginformation from monitoring media drives based on when a media is in amedia drive. By monitoring tape sessions, the degradation andreliability of system components can be monitored, allowing unreliableor unacceptably degraded components to be identified, thus allowing forthe unreliable or degraded components to be bypassed or replaced,enhancing the reliability of the system and proactively preventing dataloss.

Embodiments can be utilized in conjunction with monitoring systems forvarious media including magnetic tapes and optical disks. While variousembodiments are disclosed with reference to tape systems, embodimentscan be used with other media systems. FIG. 1 is a diagrammaticrepresentation of one embodiment of a tape library, as would beunderstood by one of ordinary skill in the art. Library 100 can comprisedrives 140 a-140 e, media changer 125 and associated robot 130,import/export element(s) 145 and slots 135 a-135 j. Drives 140 a-140 ecan read/write data from/to magnetic tape (contained within cartridges),eject tape cartridges, and perform other operations. Slots 135 a-135 jstore the magnetic tape cartridges when they are not in a drive androbot 130 moves the magnetic tape cartridges between drives 140 a-140 eand slots 135 a-135 j. For example, robot 130 may move a tape cartridgestored at slot 135 a to drive 140 b so that data can be written to thetape cartridge. It should be noted that some libraries may employ asingle robot or multiple robots in an expandable or modularconfiguration.

A Read Element Status (RES) command is a command which is used to pollthe state of a library. That is, a RES command is sent to a library andin response, the library returns its current state, including thelocations of individual tape cartridges. Thus, a RES command provides asnapshot of a library at any one time. Examples of a RES command can befound in section 6.5 of NCITS T10/999D Revision 10 a Specification,section 6.10 of INCITS T10/1383D Revision 7 Specification and section6.10 of INCITS T10/1730-D Revision 5 Specification; all of theabove-mentioned Specifications (the “T10” specifications) are herebyincorporated by reference.

A Read Media Serial Number (RMSN) command is a command which is used todetermine the serial number of a tape in a drive. The RMSN command issent to a drive and in response, the drive returns the vendor assignedserial number of the tape, if a tape is in the drive. If the tape has noserial number, the response indicates that no serial number is presenteven though a tape is in the drive. If the drive contains no tape, theresponse includes an indication that no media is present in the drive(a.k.a. as a “Check Condition” response). Examples of a RMSN command canalso be found in the T10 specifications.

A Log Sense (LS) command is a command which is used to obtain dataassociated with a particular drive. A LS command is sent to a particulardrive of a library and in response, the drive returns data associatedwith the drive and/or the media contained in the drive depending on theactual LS command. For example, such data might include: read errors,write errors, utilization and performance data, data regarding the datawritten and read to a media, media loaded, detail tables or other data.In one embodiment, the amount of data written over a period of time maybe derived from data returned in response to one or more LS commands.More specifically, data returned in response to an LS command mayinclude Log Sense page 0xC, 0x32 or 0x39 which may include data fromwhich the amount of data written by a particular drive over a period oftime may be derived (e.g., calculated). Examples of a LS command can befound in “SCSI Primary Commands-3 (SPC-3)”, (Project T10/1416-D),Revision 22a, Mar. 25, 2005, propagated by the T10 Technical Committeeof the InterNational Committee on Information Technology Standards(INCITS), which is hereby incorporated by reference.

An Inquiry command is a command that is used to query relatively staticinformation (e.g., serial number, manufacturer or other relativelystatic information) from components of a library such as a drive or amedia changer. According to one embodiment, Inquiry commands are used toquery individual library components. That is, an individual Inquirycommand may query a particular library component. Examples of an Inquirycommand can be found in “SCSI Primary Commands-3 (SPC-3)”, (ProjectT10/1416-D), Revision 22a, Mar. 25, 2005, propagated by the T10Technical Committee of the InterNational Committee on InformationTechnology Standards (INCITS), referenced above. Embodiments of theinvention can utilize a monitoring appliance which can be a Read VerifyAppliance (RVA). The monitoring appliance polls the state of a libraryover time by sending RES commands to the library at intervals. Returnedlibrary states are compared. Based on the comparison between thereturned library states, the movement of tape cartridges over time canbe tracked and the beginning and ending of tape sessions can beidentified. One example of tracking movement of media is found in U.S.patent application Ser. No. 11/801,809, filed on May 11, 2007, entitled“Method and System for Non-Intrusive Monitoring of Library Components”,by Foster et al., which is incorporated herein as if set forth in full.

Various embodiments identify tape (or other media) sessions whichrepresent the period of time that a tape is in a tape drive or otherselected location. Tracking tape sessions allows sources of errors to beidentified. For example, an individual tape cartridge may suffer from anincreasing number of data errors in any drive: this implies that thetape cartridge is degrading and may require replacement. In anotherexample, a tape cartridge may encounter errors when used with a tapedrive A but may encounter no errors when used with other tape drives. Ifother tape cartridges encounter errors when used with tape drive A, butencounter no errors when used with other tape drives, this implies thattape drive A is unreliable. Accordingly, tape drive A may be bypassed orreplaced. Some errors, though, do not appear to correlate to either aparticular tape or to a particular drive. In many instances, these typesof errors may correlate with influences external to the tapes and tapedrives. By tracking tape sessions, errors can be correlated to theseother influences.

FIG. 2 is a diagrammatic representation of a system 200 in which aplurality of hosts 202 a-202 d have access to library 100 over network205. Network 205 can comprise the Internet, a SAN, a LAN, a WAN, awireless network, or any other communications network known in the art.Hosts 202 a-202 d are coupled to library 100 via network 205 and switch207. Similarly, library 100 can communicate with switch 207 over anysuitable communications link or network known in the art and can useadditional protocols such as iSCSI, TCP/IP, or other protocol known inthe art. Switch 207 is connected to monitoring appliance 220.

Switch 207 is connected to library 100. Thus, switch 207 can forward REScommands from monitoring appliance 220 to library 100. Switch 207receives the library state generated in response to the RES command fromlibrary 100 and forwards the library state to monitoring appliance 220which stores the library state and/or compares it with one or moreprevious library states. Thus monitoring appliance 220 can continuallypoll the state of library 100, track tape movements and monitor thecomponents of library 100. It should be noted that the intervals betweenpolling can be fixed periods of time or of variable duration or acombination of the two. In one embodiment, the monitoring appliancepolls a library every 30 seconds. In another embodiment, the timeduration between polling is less than the backup time or the tapemovement time. In embodiments of the invention, the intervals can bedetermined by computer algorithm or user input. Because monitoringappliance 220 tracks tape movements using RES commands, monitoringappliance 220 does not need to intercept commands or responses fromnetwork 205 to track tape movements. Thus, in one embodiment, monitoringappliance 220 can be an out-of-band appliance. This allows monitoringappliance 220 to be a non-intrusive device which does not monitor orinterfere with commands from and responses to hosts 202 a-202 d.Consequently, monitoring appliance 220 can be a compartmentalized devicewhich can be coupled to a switch and which does not have to beintegrated into network 205. An advantage of this out-of-bandmethodology is that a monitoring appliance can be used to monitorlibrary components without cumbersome configuring.

While shown as a physical media library in FIG. 2, library 100 can be avirtual media library that is a virtual representation of one or morephysical media libraries as presented by switch 207, a librarycontroller, or other component. Examples of library virtualization aredescribed in U.S. patent application Ser. No. 10/704,265, entitled“System and Method for Controlling Access to Multiple Physical MediaLibraries”, and U.S. patent application Ser. No. 10/703,965, entitled“System and Method for Controlling Access to Media Libraries”, both ofwhich are hereby incorporated by reference herein.

FIG. 3 is a diagrammatic representation of a monitoring applianceController 300 (“controller 300”). Controller can include a processor302, such as an Intel Pentium 4 based processor (Intel and Pentium aretrademarks of Intel Corporation of Santa Clara, Calif.), a primarymemory 303 (e.g., RAM, ROM, Flash Memory, EEPROM or other computerreadable medium known in the art) and a secondary memory 304 (e.g., ahard drive, disk drive, optical drive or other computer readable mediumknown in the art). A memory controller 307 can control access tosecondary memory 304. Controller 300 can comprise a communicationsinterface 306 (e.g., fibre channel interface, Ethernet port or othercommunications interface known in the art) to connect controller 300 toswitch 207. An I/O controller 312 can control interactions with switch207. Similarly, an I/O controller 314 can control interactions over I/Ointerfaces 308 and 310. Controller 300 can include a variety of inputdevices. Various components of controller 300 can be connected by a bus326.

Secondary memory 304 can store a variety of computer instructions thatinclude, for example, an operating system such as a Windows operatingsystem (Windows is a trademark of Redmond, Wash. based MicrosoftCorporation) and applications that run on the operating system, alongwith a variety of data. More particularly, secondary memory 304 canstore a software program 330 that monitors tape sessions. Duringexecution by processor 302, portions of program 330 can be stored insecondary memory 304 and/or primary memory 303.

FIG. 4 is a flow chart illustrating method 400 for monitoring tapesessions associated with library 100 or individual tape drives 130.Method 400 can begin with monitoring appliance 220 of FIG. 2 pollinglibrary 100 via a RES command (for example) at step 402. In response tothe poll of step 402, library 100 returns a snapshot of the status ofthe components of library 100 including information regarding slots 135,drives 140, and the tapes therein. Successive polls of library 100 canbe compared at step 404. If the current poll, when compared with theprevious poll, indicates that a tape has been loaded into a drive 140 anew tape session may be initiated at step 406. Monitoring application220 may receive the tape number, the tape drive 140 number, and the tapedrive 140 serial number involved in the information returned with theRES command response. If no tape has been loaded, then monitoringappliance 220 can continue polling library 100 as shown at step 402until a change of status occurs with respect to the loading andunloading of tapes in to and out of drives 140. If a tape was already indrive 140, or if a tape session began at step 406, monitoring appliance220 can monitor the tape session at step 408. In step 409 monitoring oflibrary 100 as a whole, drives 140, or the components of library 100 cancontinue at all times during method 400.

FIG. 8 is a flow chart illustrating one embodiment of a method forcollecting data and organizing the collected data so that it can beaccessed by or displayed to a user. According to one embodiment, themethod of FIG. 8 can be implemented as a set of computer executableinstructions stored on a computer readable medium at, for example,monitoring appliance 820. The set of computer executable instructionscan, when executed, collect data associated with library components in anon-intrusive manner. At collect data step 810, data is collected by amonitoring appliance by querying library components of a library fordata by sending commands corresponding to the library components to thelibrary components. In response, the library components return dataassociated with the library components. More specifically, in oneembodiment, RES, Log Sense (LS), and Inquiry commands are sent tolibrary components and, in response, the library components returncorresponding data. Data may be collected over time by collecting datafrom library components at intervals. For example, various commands canbe sent every 10 seconds, every 20 seconds or with any other frequency.Thus, over time, library components may be queried a plurality of times,and as a result, the repository may contain data regarding librarycomponents at different points in time.

The monitoring appliance, at compile data step 820, can compile thereturned data. For example, the monitoring appliance can compile thedata in defined structures (e.g., XML structures or other structures). Astructure may contain data associated with a library component returnedin response to one or more commands (e.g., RES, LS, or Inquirycommands). For example, a XML structure can include data from REScommands and serial numbers of library components determined fromInquiry commands issued to corresponding library components. At storedata step 830, the monitoring appliance stores the returned data in arepository. Storing data in a repository may comprise storing structuresin the repository or may comprise unpacking returned data compiled atcompile step 820 and storing the data in the repository. In oneembodiment, the data may be stored in records in a database at therepository.

At organize data step 840, the data in the repository is organized. Aspart of step 840, data in the repository can be arranged inchronological order and/or superfluous or redundant data can be purged.Corresponding data can be grouped together. For example, data structurescorresponding to a particular drive may be arranged in chronologicalorder within the repository.

At process data step 850, data in the repository may be processed todisplay desired data to a user. For example, a user may only want to seedata corresponding to a particular library component. At process datastep 850, the data in the repository is processed such that the desireddata is selected to be displayed to a user. Similarly, data may beprocessed into graphs or charts, or in accordance with any number ofpurposes or user desires.

In one embodiment, processing data in the repository can comprisecomparing returned library states or data regarding the locations ofindividual tape cartridges stored in the repository to track themovement of one or more tape cartridges. For example, data in therepository corresponding to different times can be compared and themovement of tape cartridges in a library tracked by differencing thelocations of tape cartridges in a library at different times. Inembodiments in which data is stored in records in a database, recordsassociated with different times may be compared to track the movement oftape cartridges. Processing data can further comprise correlating errorswith a particular library component based on the movement of one or moretape cartridges within the library. Additional information regardingmonitoring libraries is disclosed in U.S. patent application Ser. No.11/801,809, filed on May 11, 2007, entitled “Method and System forNon-Intrusive Monitoring of Library Components,” by Foster et al. and ofU.S. patent application Ser. No. 12/024,755, filed on Feb. 1, 1998,entitled “Media Library Monitoring System and Method,” by Sims, now U.S.Pat. No. 7,908,366, which is incorporated herein as if set forth infull.

Performance monitored in accordance with the embodiment of FIG. 8, orother methods of monitoring performance data, can be correlated withtape sessions in some embodiments. Turning briefly to FIG. 5, FIG. 5illustrates two tape sessions 502 and 504 and performance 505 and 508associated therewith. As FIG. 5 shows, tapes A1234 and B5678 wereinvolved in tape sessions 502 and 504. Tape session 502 shows a higherand steady performance 506 when compared to the lower and erraticperformance 508 of tape session 504. Performance 508 exhibits a peak 510after a gradual build up and shifting low-level performance thereafterwhich leads to a low performance plateau 512 with which tape session 504ends. Tape session 504 may adversely affect the performance of system200 of FIG. 2 whether the cause of the low performance of tape session504 is the tape, the drive 140, or some other factor either internal orexternal to library 100. For instance, any of a number of components ofsystem 200 could slow the data delivery rate to library 100.

Returning to FIG. 4, monitoring appliance 220 can continue monitoringperformance 506 and 508 of library 100 until, at step 410, when itdetects that the tape involved in tape session 502 and 504 is unloadedfrom the drive 140. Monitoring appliance 220 may then end (at step 412)tape session 502 or 504 depending on which tape A1234 or B5678 moved.The performance information gathered during tape session 502 or 504 maybe output, stored, or further processed at step 414. If the user desiresno further tape session monitoring, step 416 shows that monitoringapplication 220 of FIG. 2 may stop monitoring library 100. If the userwishes to continue monitoring tape sessions, step 416 shows that suchmonitoring may continue by returning to step 402 and cycling throughselected portions of method 400 to detect tape loads and unloads and tomonitor performance during tape sessions.

Users can review performance 506 and 508 related information gatheredduring tape sessions 502 and 504 to identify low performance tapesessions such as tape session 504 at step 418. Users can also identifythe causes for the low performance session 504 at step 420 frominformation gathered during tape sessions 502 and 504 as well as otherinformation available to the users. For instance, if tape session 504was associated with host 202 b of FIG. 2 and shows low performance 508,host 202 b and system 200 components between host 202 b and library 100may be examined to determine if they might be the cause of lowperformance 508. Underperforming portions of system 200 may be replacedto improve performance 508.

FIGS. 6 and 7 show reports 600 and 700 which monitoring appliance 220may display for users of system 200. FIG. 6 shows a tape status report600 for the last 24 hours for library 100 and FIG. 7 shows tape statusreport 700 for the last 24 hours for a single drive 140. Report 600 canbe sorted by time of tape insertion into a drive and shows performancedata associated with a collection of drives. Each line of report 600 canrepresent a tape session such as tape sessions 602, 604, and 606. Report600 can also display, for each tape session 602, 604, and 606, theidentity 608 of a tape in a drive, the slot 610 in which the tape isstored when not in use, the drive number 612 of the drive involved, theserial number 614 of the drive, the time 616 at which the tape wasloaded, the total time 618 during which the tape was loaded in thedrive, the amount of data 620 read to or written from the tape,performance 622 (here data transfer rate in GBytes), and the overallstatus 624 of tape session 602, 604, or 606.

FIG. 6 illustrates a query from a database in to which informationobtained from polling library 100 is stored. For instance, tapeidentities 608 may originate from bar code tags on the tapes. Foranother example, slot numbers 610 can correspond to slots 135 of FIG. 2.In-drive time 618 can be computed by subtracting the clock time of thepoll which detected the beginning of session 602, 604, or 606 from theclock time of the poll which detected the ending of tape session 602,604, or 606. Another way in which in-drive time 620 can be calculated isto subtract the times reported by library 100 at which a tape was loadedand unloaded for tape sessions 602, 604, or 606. Many other types ofperformance information can be reported in report 600. For instance,instead of reporting amount of data transferred 620, the number of reador write errors could be reported. Another example of information whichmay be reported is performance 622 which is shown as a rate determinedby dividing data amount 620 by in-drive time 618. For instance, tapesession 602 is shown as having a performance 622 of 33 MB/sec. Tapesession 604 shows performance 622 of 7 MB/sec. Tape session 606illustrates a case in which performance 622 was 0 MB/Sec.

Other performance related information may be reported by report 600 suchas the room temperature, room humidity, or the personnel on call duringvarious tape session 602, 604, and 606. Tape session status 624 couldcorrespond to the status of tape drive 140, the tape, library 100, etc.Tape session status 624 could also report information such as the numberof errors which occurred during tape sessions 602, 604, or 606. Otherfeatures of report 600 could serve to call attention to informationreported therein. For instance, if the number of errors during a sessionrose beyond a user selected limit, the row of report 600 correspondingto relevant tape session 602, 604, or 606 could be color coded, could beconfigured to flash, or could be configured to draw attention to itselfin some other manner.

Users can peruse information 608, 610, 612, 614, 616, 618, 620, 622, and624 (for example) in report 600 and identify low performing sessions606. Users can also correct or optimize system 200 performance relatedto low performance tape session 606. Such activity can obviate thedesire to purchase additional libraries 100 when library 100 may not bethe reason for low performance tape sessions 606. For instance, library100 to which FIG. 6 pertains has a specified data transfer rate of 80MB/sec. An inspection of FIG. 6 reveals that only a few tape sessionsachieved even about half of the specified rate. Reports such as report600 can reveal many other aspects of system 200 performance. Forinstance, while some back up operations can span several tapes, FIG. 6reveals that library 100 loaded and unloaded tape number 00058 numeroustimes. It is possible that determining why such activity occurred mightreveal an aspect of system 200 which could be corrected or optimized.

FIG. 7 illustrates that for a single tape drive (of library 200 or astand-alone drive) report 700 can be a list of tapes that were loadedinto the drive. In FIG. 7, report 700 is sorted by the time the tapeswere loaded in to drives 140. Monitoring appliance 200 could alsogenerate reports such as reports 600 or 700 for each individual tape insystem 200 showing when the tapes were loaded into each of a variety ofdrives 140. Appliance monitor 220 could also display additionalinformation regarding the tapes, drives 130, and tape sessions 502 and504. For example, performance curves 506 and 508 of FIG. 5 could bedisplayed with reports 600 and 700. For another example, monitoringappliance 220 could display which tapes were in which drives 140 duringthe time that the data for performance curves 506 and 508 were gathered.In some embodiments, reports 600 and 700 and other performance relatedinformation can be delivered by a world-wide-web based interface,e-mail, SCSI or SNMP reporting mechanisms, etc.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,product, article, or apparatus that comprises a list of elements is notnecessarily limited only those elements but may include other elementsnot expressly listed or inherent to such process, product, article, orapparatus. Further, unless expressly stated to the contrary, “or” refersto an inclusive or and not to an exclusive or. For example, a conditionA or B is satisfied by any one of the following: A is true (or present)and B is false (or not present), A is false (or not present) and B istrue (or present), and both A and B are true (or present).

Additionally, any examples or illustrations given herein are not to beregarded in any way as restrictions on, limits to, or expressdefinitions of, any term or terms with which they are utilized. Instead,these examples or illustrations are to be regarded as being describedwith respect to one particular embodiment and as illustrative only.Those of ordinary skill in the art will appreciate that any term orterms with which these examples or illustrations are utilized willencompass other embodiments which may or may not be given therewith orelsewhere in the specification and all such embodiments are intended tobe included within the scope of that term or terms. Language designatingsuch nonlimiting examples and illustrations includes, but is not limitedto: “for example”, “for instance”, “e.g.”, “in one embodiment”.

Although embodiments have been described in detail herein, it should beunderstood that the description is by way of example only and is not tobe construed in a limiting sense. It is to be further understood,therefore, that numerous changes in the details of the embodiments andadditional embodiments will be apparent, and may be made by, persons ofordinary skill in the art having reference to this description. It iscontemplated that all such changes and additional embodiments are withinscope of the claims below.

What is claimed is:
 1. A monitor appliance for a media library, themonitor appliance comprising: a processor; and a computer memoryelectronically connected to the computer processor, the computer memorystoring a set of computer instructions executable by the computerprocessor for: polling the media library to determine the position of astorage media in the media library; establishing a media sessionassociated with the storage media corresponding to a time period inwhich the storage media is loaded in a drive of the media library;polling the media drive during the media session for performanceparameters representing the performance of the media drive; andassociating performance data based on the performance parameters withthe media session.
 2. The monitor appliance of claim 1, wherein theinstructions are further executable for presenting the performance datato a user in a manner that allows the use to identify the media session,associated storage media and associated performance data.
 3. The monitorappliance of claim 1, wherein the polling the media library furthercomprises sending a Read Element Status command to the media library. 4.The monitor appliance of claim 1, wherein the media library is amagnetic tape library and the storage media is a magnetic tape.
 5. Themonitor appliance of claim 1, wherein the polling is out-of-band.
 6. Themonitor appliance of claim 1, wherein the instructions are furtherexecutable for: determining in to which of a plurality of media drivesthe storage media has been loaded; determining which of a plurality ofstorage medium has been loaded in to the media drive; and associatingthe performance with the storage media which has been loaded in to themedia drive and with the media drive in to which the storage media wasloaded.
 7. The monitor appliance of claim 1, wherein the instructionsare further executable for creating a list of media sessions sorted byperformance.
 8. The monitor appliance of claim 1 wherein theinstructions are further executable for, when the performance is slow,determining whether the cause of the slow performance is external to themedia library.
 9. The monitor appliance of claim 8 wherein theinstructions are further executable for correcting the external cause ofthe slow performance.
 10. A monitor system for a library, the monitorcomprising: a processor; and a computer memory electronically connectedto the computer processor, the computer memory storing a set of computerinstructions executable by the computer processor to: poll the libraryat intervals to determine a position for a storage media in the library,determine from the polled positions of the media whether the media hasbeen loaded in to, or unloaded from, a drive of the library, when themedia has been loaded in to the drive, begin a media session; monitorthe performance of the library while the media is loaded in the driveand associate performance data determined from the monitoring with themedia session; when the media has been unloaded from the drive, end themedia session; and output information associated with the media session.11. The monitor system of claim 10, wherein the computer instructionsare further executable to determine in to which of a plurality of drivesthe media has been loaded.
 12. The monitor system of claim 10, whereinthe computer instructions are further executable to determine which of aplurality of medium has been loaded in to the drive.
 13. The monitorsystem of claim 10, wherein polling the library comprises sending a ReadElement Status command to the library.
 14. The monitor system of claim10, wherein the library is a magnetic tape library and the media is amagnetic tape.
 15. The monitor system of claim 10, wherein the monitorsystem is at least a portion of an out-of-band appliance.
 16. Themonitor system of claim 10, wherein the polling is out-of-band.
 17. Themonitor system of claim 10, wherein the computer instructions arefurther executable to: determine in to which of a plurality of drivesthe media has been loaded; determine which of a plurality of medium hasbeen loaded in to the drive; and associate the performance with themedia which has been loaded in to the drive and the drive in to whichthe media was loaded.
 18. The monitor system of claim 10, wherein thecomputer instructions are further executable to create a list of mediasessions sorted by performance.